-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix: reinstate tests #2368
Fix: reinstate tests #2368
Conversation
Hmm, the last 2 about permission and wildcard tests were things I recently added which leverages the embedded db_unit test framework...i'm wondering why it doesn't work across a full test but I'm sure it ran on the individual ones (even both those together as I ran the entire test class). I can pull down this branch and try to run the entire suite in debug and see if there's something that is a side-effect of the other tests that interfere with running this one test |
Thanks @chrisknoll . I'm looking at the |
8b49e90
to
707b173
Compare
This allows the other tests to be reinstated while these two can then be fixed separately.
@chrisknoll the tests you mentioned seem to fail only at the DELETE step: loadPrepData(testDataSetsPaths, DatabaseOperation.DELETE); |
Thanks, I'm on a bit of a crunch and haven't' been able to dig in. But the DatabaseOperation.DELETE is where it's suppsoed to take the test data that is in the prep data set and delete any row that matches the data in there (effectively removing the rows that were inserted at the start of the test). I'll have to run through it by hand to trace through what part of it is failing the delete...is it a FK delete order problem? not sure yet....but I'm sure I can figure it out. |
It seems to fail at
|
@chrisknoll should I just disable the two |
This allows the other tests to be reinstated while these two can then be fixed separately.
...this one seems to only work depending on the order of execution... it lacks the setup() method where a pre-filled db is guaranteed, like for example in CohortCharacterizationServiceTest
StudyInfoTest also started failing (side effect?), so I disabled that as well:
Summary: 5 unit tests have been disabled. The rest seems to be passing now ✅ :
The
or
Somehow the IT tests step finished with SUCCESS, so the errors are not being detected correctly. To be solved in a separate ticket, together with the disabled tests above perhaps. |
Reinstate tests, rolling back what was done in #1903
As far as I can see, there are just 4 same tests (out of 220) that always fail:
I would advocate for only skipping these 4 for now instead of skipping all 220.